projects / xen.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 88381e5) | patch
bitkeeper revision 1.1159.223.75 (42078dd8VBcyJ0X9yF-bRHcBVUJ3Ww)
authoriap10@labyrinth.cl.cam.ac.uk <iap10@labyrinth.cl.cam.ac.uk>
Mon, 7 Feb 2005 15:48:40 +0000 (15:48 +0000)
committeriap10@labyrinth.cl.cam.ac.uk <iap10@labyrinth.cl.cam.ac.uk>
Mon, 7 Feb 2005 15:48:40 +0000 (15:48 +0000)
commitd08dd0ac713846d51d52b8ee90a73a347c97dfb8
treef635c688709b97444f9c368bd777dc1c621612aetree | snapshot
parent88381e599a556df1b6d7ee03cfeaa1c822083488commit | diff
bitkeeper revision 1.1159.223.75 (42078dd8VBcyJ0X9yF-bRHcBVUJ3Ww)

As pointed out on the xen-devel list, the vm86 call was not very robust in
Xen.
It turned out to be due to a missing check in the pagefault handler,
determining whether the pagefault came from userspace or from the kernel.
Now the syscall-crash tool doesn't cause any "Oops" on the vm86 calls anymore.

From: Stephan Diestelhorst <sd386@cam.ac.uk>
Signed-off-by: ian.pratt@cl.cam.ac.uk
linux-2.6.10-xen-sparse/arch/xen/i386/mm/fault.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.